- Inner Source—Adopting Open Source Development Practices in Organizations
- Adopting InnerSource: Principles and Case Studies
- Application of inner source on small development teams - A case study
- Dirk Riehle: "Ten Years of Inner Source: Case Studies & Conclusions"
- A comparative study of challenges in integrating Open Source Software and Inner Source Software
- Case studies of Inner Source
- Promoting Software Reuse in a Corporate Setting
Discover gists
| RAR registration data | |
| WinRAR | |
| Unlimited Company License | |
| UID=4b914fb772c8376bf571 | |
| 6412212250f5711ad072cf351cfa39e2851192daf8a362681bbb1d | |
| cd48da1d14d995f0bbf960fce6cb5ffde62890079861be57638717 | |
| 7131ced835ed65cc743d9777f2ea71a8e32c7e593cf66794343565 | |
| b41bcf56929486b8bcdac33d50ecf773996052598f1f556defffbd | |
| 982fbe71e93df6b6346c37a3890f3c7edc65d7f5455470d13d1190 | |
| 6e6fb824bcf25f155547b5fc41901ad58c0992f570be1cf5608ba9 |
| { | |
| "$schema": "http://json-schema.org/draft-07/schema#", | |
| "title": "Hytale Item Configuration Schema - Fully Documented", | |
| "description": "Complete JSON Schema for Hytale Item asset configuration with comprehensive documentation including full Java package references, field mappings, and enumeration details. All properties are documented with line numbers and source code references.", | |
| "type": "object", | |
| "required": ["Id"], | |
| "additionalProperties": false, | |
| "properties": { | |
| "Id": { | |
| "type": "string", |
| // This code demonstrates a simplified "stackification" algorithm to turn | |
| // instructions in a basic block back into a tree. This is useful when | |
| // generating WebAssembly code from assembly instructions in SSA form. | |
| // | |
| // It's the algorithm used by LLVM's WebAssembly backend, viewable here: | |
| // https://github.com/llvm-mirror/llvm/blob/master/lib/Target/WebAssembly/WebAssemblyRegStackify.cpp | |
| type InsKind = | |
| 'Add' | | |
| 'LocalSet' | |
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.
| { config, pkgs, lib, ... }: { | |
| imports = [ | |
| (import <nixpkgs/nixos/modules/system/etc/etc.nix>) | |
| ]; | |
| options.system.build.etc = lib.mkOption { type = lib.types.package; }; | |
| options.system.activationScripts.etc = | |
| lib.mkOption { type = lib.types.unspecified; }; | |
| config = { |
The following is a quick guide on getting basic status LED functionality working with TrueNAS running on the UGREEN DXP4800 Plus. Theoretically, it should work on all models (with some small revisions to the script), but I only have a DXP4800 Plus. :)
This guide is for cron job that runs a script to update the LEDs every couple minutes, but I'm sure the following can be modified for blinky LEDs as well.
| # Semi-Secret | |
| actualities.google.com – alias for news.google.com | |
| d.google.com – same as www.google.com | |
| email.google.com – redirects to mail.google.com (obviously) | |
| fusion.google.com – redirects to www.google.com | |
| locale.google.com – redirects to local.google.com | |
| purchase.google.com – same as www.google.com | |
| relay.google.com – nothing (possibly a mail relay server?) |
